Dynamic latency-based rerouting

ABSTRACT

A switch creates and dynamically updates a latency map of a network to adjust routing of flows. Further, the network is monitored to detect latency issues and trigger a dynamic adjustment of routing based on the latency map. In this manner, a flow can be routed along a route (i.e., a faster route) that provides less latency than other available routes. The latency map can be generated based on latency probe packets that are issued from and returned to the source switch. By evaluating many such latent probe packets that have traveled along many available routes (e.g., corresponding to various ports of the switch), the switch or associated administrative logic can dynamically adjust the latency map to updated latency information of available routes. Therefore, responsive to a trigger, the source switch can dynamically adjust the routing of a flow based on latency issues discerned from the network.

BACKGROUND

With some networks, communication between one node and another node(e.g., a server and a storage device) may be possible via multipleavailable routes through the network. Such communication is embodied ina sequence of transmitted data frames or a “flow” between the sourcenode and the destination node, wherein the flow typically represents asingle session or data exchange within a specific protocol. The flowenters the network at a source switch connected to the source node andleaves the network at a destination switch connected to the destinationnode.

When the source switch receives a frame of a flow, the source switchchecks its routing table to determine whether a route though the networkhas already been assigned to the flow. If a route has already beenassigned, the source switch transmits the frame via the egress portcorresponding to the assigned route. If a route has not already beenassigned, the source switch selects a route over which to transmit theflow along one of the multiple paths through the network and records theselected route in the routing table.

Typically, such a selection is performed randomly and/or withoutsignificant knowledge of downstream network characteristics, andtherefore the selected route may not offer the best performance. Inother words, in some circumstances, another available route may haveprovided better performance but it was not selected. In such cases,after that initial selection, the flow is fixed to the lower performanceroute for the flow's duration (e.g., until the server/storage exchangecompletes and the flow terminates). For example, a flow may be routedthrough a part of the network that includes slow switches and/orcongested links, while other routes were available that do not includesuch slow switches or congested links. Yet, by virtue of the initialroute selection, the flow remains bound to the slower route until itscompletion. Such route selection can result in non-optimal routing,particularly for latency-sensitive flows.

Further, network performance can change as the traffic through variousnetwork links changes. Therefore, even if an optimal route is initiallyselected for a given flow, the route may later change to have excessivelatency while other routes could provide a lower latency. However, nosolutions exist to dynamically adjust routing based on latencydistributions and changes in a network.

SUMMARY

Implementations described and claimed herein address the foregoingproblems by creating and dynamically updating a latency map of thenetwork to adjust routing of flows. Further, the network is monitored todetect latency issues and trigger a dynamic adjustment of routing basedon the latency map. In this manner, a flow can be routed along a route(i.e., a faster route) that provides less latency than other availableroutes. In a switch handling many flows, rerouting can be accomplishedby adjusting congestion mapping among multiple routes, such that routingone or more flows to a lower latency route is favored over routing to ahigher latency route. In this manner, some of the flows are rerouted tothe lower latency route, which in turn lowers the latency of the higherlatency route. The latency map can be generated based on latency probepackets that are issued from and returned to a switch in the network(e.g., a source switch). The latency probe packets are periodically sentto various flow destinations and returned to the switch at the flowsource. By evaluating many such latent probe packets that have traveledalong many available routes (e.g., corresponding to various ports of theswitch), the switch or associated administrative logic can dynamicallyadjust the latency map to updated latency information of availableroutes. Therefore, responsive to a trigger, the switch can evaluate theupdated latency map and select a faster route among all of the routecandidates by which to reroute one or more flows.

Other implementations are also described and recited herein.

BRIEF DESCRIPTIONS OF THE DRAWINGS

FIG. 1 illustrates an example topology of a local area network (LAN) anda storage area network (SAN) employing dynamic latency-based routing.

FIG. 2 illustrates an example network in which a source switch hastransmitted latency probe packets along multiple available routes.

FIG. 3 illustrates an example network in which a destination switch hasprepared latency probe packets for return to the source switch.

FIG. 4 illustrates an example network in which a destination switch hastransmitted latency probe packets back to the source switch, whichupdates the latency map of its available routes.

FIG. 5 illustrates an example destination switch processing a latencyprobe packet (L) in a transmit queue.

FIG. 6 illustrates an example destination switch processing a latencyprobe packet (L) at the head of a transmit queue.

FIG. 7 illustrates an example destination switch transmitting a latencyprobe packet (L) to the source switch.

FIG. 8 illustrates an example network in which a switch is signaling thesource switch about detected congestion.

FIG. 9 illustrates an example network in which latency of a route hasexceeded a predetermined threshold.

FIG. 10 illustrates example operations for maintaining a latency map.

FIG. 11 illustrates example operations for dynamically adjusting routingfor a flow.

FIG. 12 illustrates example operations for returning a latency probepacket.

FIG. 11 illustrates an example switch architecture configured toimplement dynamic latency-based rerouting.

DETAILED DESCRIPTIONS

FIG. 1 illustrates an example topology 100 of a local area network (LAN)102 and a storage area network (SAN) 104 employing dynamic latency-basedrouting. As described, dynamic latency-based routing can be employed ineither or both of the LAN 102 and the SAN 104, as well as in othernetworks, such as a metropolitan area network (MAN), and in networksemploying a variety of networking protocols, such as Ethernet, FibreChannel, Infiniband, etc.

With respect to the LAN 102, FIG. 1 depicts three client nodes 105, 106,and 107 connected to a source switch 108. The LAN 102 can beEthernet-based or employ another networking protocol, including bothwired and wireless protocols. The source switch 108 is connected withinthe LAN 102 with edge switch 110 via switches 112 and 114. The edgeswitch 110 then connects to destination nodes, servers 116 and 118. Ifthe client node 106 communicates with the server 116 to access an emailserver function, a flow would be defined between the client node 106 andthe server 116 (e.g., based on a source address of the client node 106and the destination address of the server). The source addressrepresents a type of source identifier (abbreviated herein as “SID”),and the destination address represents a type of destination identifier(abbreviated herein as “DID”).

In the illustrated topology, the source switch 108 has two availableroutes to communicate the flow through the LAN 102 from the client node106 and the destination server 116: (1) via the switch 112 and (2) viathe switch 114. Once selected, the flow's route is traditionally fixedfor the duration of the flow. However, using dynamic latency-basedrouting, the source switch 108 can detect a latency condition within theLAN 102 and trigger a rerouting to redirect the flow (or one or moreother flows) to another available route. For example, the source switch108 can initially communicate the flow via the switch 112, detect alatency condition along that route, and therefore reroute the flowthrough the switch 114 based on a latency map of the LAN 102.

With respect to the SAN 104, FIG. 1 depicts the two servers 116 and 118connected to a source switch 120. The SAN 104 can be Fibre Channel-basedor employ another networking protocol, including both wired and wirelessprotocols. The source switch 120 is connected within the SAN 104 withedge switch 122 via switches 124 and 126. The edge switch 110 thenconnects to destination storage nodes 128, 130, and 132. If the server116 communicates with the destination storage node 130 to access emaildata, a flow would be defined between the server 116 and the destinationstorage node 130 (e.g., based on a source identifier (SID) of the server116 and the destination identifier (DID) of the destination storage node130).

In the illustrated topology, the source switch 120 has two availableroutes to communicate the flow through the LAN 104 from the server 116and the destination storage node 130: (1) via the switch 124 and (2) viathe switch 126. Once selected, the flow's route is traditionally fixedfor the duration of the flow. However, using dynamic latency-basedrouting, the source switch 120 can detect a latency condition within theSAN 104 and trigger a rerouting to redirect the flow (or one or moreother flows) to another available route. For example, the source switch120 can initially communicate a flow via the switch 124, detect alatency condition along that route, and therefore reroute a flow throughthe switch 126 based on a latency map of the SAN 104.

To develop a latency map of either network (e.g., the LAN 102 or the SAN104), the appropriate source switch periodically, or in response to analternative probe condition, deploys latency probe packets alongavailable routes in the network. The destination switches at the terminiof the routes send back the latency probe packets along the same route,and the source switch records the round trip travel time of the latencyprobe packet in a latency map it maintains for its available routes.When the source switch is triggered to dynamically adjust routing of oneor more flows because of a latency condition, the source switch consultsthe latency map to determine how the flows should be rerouted.

It should be understood, however, that a latency map may also bedeveloped based on one-way travel times, wherein each latency probepacket includes a transmit time stamp from the source switch and thedestination switch computes relative latencies among all of the latencyprobe packets it receives in association with a given flow. Thedestination switch can thereafter send the relative latencies back tothe source switch for inclusion in the source switch's latency map.

FIG. 2 illustrates an example network 200 in which a source switch 202has transmitted latency probe packets along multiple available routes.The example network 200 is depicted as including a source node 204, thesource switch 202, intervening switches 206 and 208, a destinationswitch 210, and a destination node 212. The source switch 202periodically, or in response to an alternative probe condition,transmits latency probe packets along the available routes to thedestination node 212 (shown by dashed arrows 214 and 216). It should beunderstood that the source switch 202 also supports other routes toother destination nodes (not shown) and may concurrently be transmittinglatency probe packets along those other routes as well.

The source switch 202 maintains a latency map 218, which is depicted inFIG. 2 as a table. In the example latency map 218, the source switch 202records a destination switch identifier (Dest), a port identifier(Port), a send time (TSend), and an effective latency time (TEff),although it should be understood that alternative values may be employed(e.g. an SID/DID combination, a real time latency time, an averagelatency time, etc.). In FIG. 2, the destination switch identifierrepresents a DID or port identifier of the destination switch 210connected to the destination node 212; the port identifier representsthe SID or port identifier of the source switch 202 connected to thesource node 204; the send time represents the time at which a latencyprobe packet is transmitted from the source switch 202; and theeffective latency time represents a measure of the latency on the routeassociated with the port identifier.

Accordingly, the latency map 218 includes two entries for the examplenetwork 200. The first row includes a destination identifier associatedwith the destination switch and/or the destination node, the portidentifier corresponding to the upper route (i.e., through the switch208), the time at which the latency probe packet 214 was transmitted,and the effective latency time of that route as computed based onprevious latency probe packets. The second row includes a destinationidentifier associated with the destination switch and/or the destinationnode, the port identifier corresponding to the lower route (i.e.,through the switch 206), the time at which the latency probe packet 216was transmitted, and the effective latency time of that route ascomputed based on previous latency probe packets. It should beunderstood that the latency map 218 would likely incorporate more thantwo rows of latency data, based on a typical network topology.

In one implementation, the latency probe packets are transmitted to thedestination switch based on the destination identifier and contains theSID of the node 204 (or the port of the source switch 202 connected tothe source node 204) and DID of the node 212 (or the port of thedestination switch 210 connected to the source node 212). In oneimplementation, the latency probe packet does not include the packettransmission time, but in other implementations, the packet transmissiontime may be carried in the latency probe packet (e.g., when usingrelative receive times at the destination switch to measure latency).Further, in one implementation, the latency probe packet includes adirection value that indicates whether the latency probe packet is onthe first leg of its round trip or on the return leg of its round trip.For example, the latency probe packets 214 and 216 would be configuredwith direction value indicating that they were on the first legs oftheir round trips.

It should be understood that, although the described technology isfocused on latency probe packets taking round trips between the sourceswitch and the destination switch, alternative implementations mayemploy uni-directional latency probe packets. Such packets aretransmitted from the source switch and received by the destinationswitch, which determines the relative latency differences among latencyprobe packets received from the source switch and sends a representationof these latency differences to the source switch. In this manner, thesource switch can maintain a latency map that reflects the latency of aroute in one direction, ignoring latency asymmetries between the legs ofa round trip. The uni-directional latencies can be employed in the samemanner as the round trip latencies discussed herein.

Furthermore, latencies of individual links can be employed. For example,each switch that receives a latency probe packet can intercept thepacket and record the intercepting switch's identifier, the time thatthe switch received the packet, and the time the switch forwarded thepacket into the payload of the packet as the packet is forwarded to thenext switch of the route. In this manner, the source switch can developa more detailed view of the route latencies at each link in the route.This link-specific (or “hop-to-hop”) latencies can be used to determinehigher performing routes within the network.

FIG. 3 illustrates an example network 300 in which a destination switch310 has prepared latency probe packets for return to the source switch302. The example network 300 is depicted as including a source node 304,the source switch 302, intervening switches 306 and 308, the destinationswitch 310, and a destination node 312. As described with regard to FIG.2, the source switch 302 sends latency probe packets to the destinationswitch 310, which returns the latency probe packets to the source switch302. As such, the destination switch 310 receives the latency probepackets from the source switch 302 and detects that it (i.e.,destination switch 310) is their intended destination and that they areon the first leg of their round trips. Accordingly, the destinationswitch 310 switches the source and destination identifiers in thelatency probe packets (shown by dashed arrows 314 and 316), modifies thedirection values to indicate return legs of the round trip, andtransmits the modified latency probe packets back to the source switch302 via their respective routes.

FIG. 4 illustrates an example network 400 in which a destination switch410 has transmitted latency probe packets back to the source switch 402,which updates the latency map 418 of its available routes. The examplenetwork 400 is depicted as including a source node 404, the sourceswitch 402, intervening switches 406 and 408, the destination switch410, and a destination node 412. The source switch 402 receives thelatency probe packets, recording a reception time stamp for each (e.g.,T3 for the upper route through switch 408 and T4 for the lower routethrough switch 406). The source switch 402 uses the reception time stampto compute an effective latency time for the route traveled by thelatency probe packet. The source switch 402 uses the various effectivelatency times of its available routes when determining how to route aflow.

In one implementation, the effective latency time measure is computedusing a weighted combination of the previous effective latency time(e.g., TL1 from FIG. 2 for the upper route) and the round trip latencytime of the most recent round trip on route (e.g., T3−T1, based on thetimes from FIG. 2 and FIG. 4 for the upper route). Accordingly, theeffective latency time measure for a route represents a contribution oflatencies measured on that route over time, potential with a weightedcombination. For example, the effective latency time measure TL3 may becomputed using the following example algorithm:

TL3=A*TL1+B*(T3−T1), where A and B are weights.

In one implementation, an example A=80% and an example B=20%, althoughother weight values may be employed. Such a weighted running averagetends to smooth out abrupt changes in latency among routes in a network,so that the effective latency time measure reflects route latency over along period of time.

In another implementation, the effective latency time measure iscomputed using a real time latency measure (e.g., T3−T1). In yet anotherimplementation, the effective latency time measure is computed using aweighted or non-weighted average over a number of latency probe packets(e.g., TL3=(TL1+(T3−T1))/(number of probes during averaged period)).Other algorithms may be employed.

FIG. 5 illustrates an example destination switch 500 processing alatency probe packet (L) in a transmit queue 502, which services anegress port 504 connected to the destination node 506. In oneimplementation (not shown), the destination switch 500 merely modifiesthe latency probe packets it receives on the first legs of their roundtrips and transmits them on the return legs of their round trips.However, in FIG. 5, the destination switch 500 inserts the latency probepacket L into the transmit queue 502 associated with the destinationnode 506, monitoring the transmit queue 502 to detect when the latencyprobe packet L arrives at the head of the transmit queue 502.

FIG. 6 illustrates an example destination switch 600 processing alatency probe packet (L) at the head of a transmit queue 602. In theillustrated implementation, when a latency probe packet arrives at thehead of the transmit queue 602, destination switch 500 extracts thelatency probe packet from the transmit queue 602 and modifies thelatency probe packet L and transmits it on the return leg of its roundtrip, as shown in FIG. 7. In this manner, the round trip latency time ofmeasured by the latency probe packet L includes the time spent by thelatency probe packet L in the transmit queue 602. Accordingly, thisapproach captures the impact of a slow draining destination node orcongested egress port.

FIG. 8 illustrates an example network 800 in which a switch 808 issignaling the source switch 802 about detected congestion. The examplenetwork 800 is depicted as including a source node 804, the sourceswitch 802, intervening switches 806 and 808, a destination switch 810,and a destination node 812.

In one implementation, the switch 808 has logic (e.g., firmware and/orhardware) configured to detect congestion at its egress ports and cantherefore notify the source switch 802 of the congestion. For example,the switch 808 may be receiving more frame traffic than one of itsoutput ports can transmit, such as influenced by a slow link between theswitch 808 and the switch 810. In such a circumstance, the switch 808can inform an administrative client (not shown), which can signal thesource switch 802 through a management port, or otherwise signal thesource switch 802 (directly or indirectly) of the congestion on a routeused by the source switch 802 (see e.g., congestion signal 814).

Based on a received congestion signal, the source switch 802 can decideto reroute a flow it knows to be routed through the congested port. Inother words, the received congestion signal acts as a trigger to causethe rerouting of any flow from the source switch 802 through thecongested port. The source switch 802 consults its latency map (notshown), waits for an acceptable time (e.g., 500 ms) to redirect theflow, and updates its routing table (not shown) to redirect the flow toa route with less latency. While waiting, the source switch 802 willhold transmission on the flow until the expiration of the wait time.

FIG. 9 illustrates an example network 900 in which latency of a routehas exceeded a predetermined threshold. The example network 900 isdepicted as including a source node 904, a source switch 902,intervening switches 906 and 908, a destination switch 910, and adestination node 912. A recent latency probing by the source switch 902has resulted in the effective latency time measures of TL3 for the routeassociated with port number 2 and TL4 for the route associated with portnumber 3, which are recorded in a latency map 918.

In one implementation, the latency map 918 also stores thresholds on aper-route basis. If the source switch 902 detects that the TEffassociated with a route used by a flow exceeds the threshold set for theroute, then the source switch 902 triggers a re-routing operation, whichevaluates the latency map, waits for an acceptable time to redirect theflow, and updates its routing table (not shown) to redirect the flow toa route with less latency. While waiting, the source switch 902 willhold transmission on the flow until the expiration of the wait time.

FIG. 10 illustrates example operations 1000 for maintaining a latencymap. A probing operation 1002 deploys a latency probe packet on a firstleg of a round trip. Typically, multiple probing operations areperformed concurrently resulting is multiple latency probe packets beingdeployed into a network. In one implementation, a source switchperiodically, or in response to an alternative probe condition,transmits latency probe packets along available routes to one or moredestination switches. For example, if the source switch has 64 egressports and services flows to 128 different destination switches, thesource switch may sends multiple latency probe packets out multipleegress ports destined for different destination switches. In oneimplementation, the latency probe packet includes a direction valueindicate that the source switch has transmitted the latency probe packeton the first leg of its round trip. The destination switch will modifythe direction value to indicate its transmission of the latency probepacket to the source switch is the return let of the packet's roundtrip.

A probe condition may be set by a timer to trigger periodic transmissionof latency probes into the network. Alternatively, other probeconditions may be employed, including physical connection of a new nodeor switch in the network, a management command from an administrativestation, receipt of a congestion signal, detection of a new flow,detection of termination of a flow, etc.

A time stamp operation 1004 records a time stamp relating to thetransmission of the latency probe packet. In one implementation, thetransmission time stamp is recorded in a field in a latency map datastructure maintained by a source switch, although latency maps may bemaintained in a central or otherwise aggregated data store (e.g., by anadministrative station).

A reception operation 1006 receives the latency probe packet on thereturn leg of its round trip. Because the destination switch modifiedthe direction value in the latency probe packet to indicate a returntrip, the source switch can detect that the latency probe packet hasreturn on its round trip.

A computation operation 1008 computes an effective latency time. In oneimplementation, the effective latency time measure is computed using aweighted combination of the previous effective latency time and theround trip latency time of the most recent round trip on route. Anexample A=80% and an example B=20%, although other weight values may beemployed. A weighted combination tends to smooth out abrupt changes inlatency among routes in a network, so that the effective latency timemeasure reflects route latency over a long period of time. In anotherimplementation, the effective latency time measure is computed using areal time latency measure. In yet another implementation, the effectivelatency time measure is computed using a weighted or non-weightedaverage over a number of latency probe packets. Other algorithms may beemployed. A recordation operation 1010 records the effective latencytime into the latency map data structure for evaluation during a dynamicrerouting operation.

FIG. 11 illustrates example operations 1100 for dynamically adjustingrouting for a flow. A maintenance operation 1102 maintains an updatedlatency map associated with a switch, such as by the example operationsdescribed with regard to FIG. 10. A decision operation 1104 determineswhether a latency condition has been detected. A variety of latencyconditions may be employed. For example, receipt of a congestion signalfrom a switch in the network may constitute a latency condition.Alternatively, an effective latency time stored in the latency map thatexceeds a configured latency threshold may constitute a latencycondition. Other factors may also or alternatively be considered aslatency conditions. If a latency condition is not detected in thedecision operation 1104, processing returns to the maintenance operation1102.

If a latency condition is detected in the decision operation 1104, anevaluation operation 1106 evaluates the latency map to determine a newroute. For example, the flow may be currently directed on a first route,and the source switch evaluates the latency map to identify anotherroute that is available to the destination switch or port and has alower effective latency time. If a better route is not found, asdetermined by a decision operation 1108, then processing proceeds to themaintenance operation 1102.

If the decision operation 1108 finds a better route (e.g., one with alower effective latency time than the existing route), then a reroutingoperation 1110 adjusts congestion mapping in the source switch, whichresults in redirection of one or more flows to the better route (e.g.,by modifying the routing table in the switch to route packets along thenew route). It should be understood that the switch may wait until it issafe to adjust the routing of the flow. For example, if the sourceswitch has not received a flow packet for transmission into the networkfor a waiting time (e.g., the amount of time set by the Fibre ChannelStandard, which is two seconds, or some other appropriate, such as 500ms), then the source switch can safely redirect the flow to a new routewithout concern about out-of-order data packets. In otherimplementations, out-of-order data packets are not an issue and so thesource switch can redirect the routing at any time. Processing thenreturns to the maintenance operation 1102.

In one implementation, the congestion mapping initially allocatesrouting to individual route on a statistical basis, wherein anindividual flow has an equal probability of being assigned to anyindividual (available) route. However, as latency conditions aredetected, the source switch adjusts that routing probability of one ormore routes, such that a lower latency route has a higher probability ofbeing selected during the rerouting than a higher latency route.Furthermore, the dynamic adjustment process can be incrementally imposedso that when a particular route exhibits a latency condition, therouting probability is shifted by some predefined or computed amount infavor of the lower latency routes. If a latency condition occurs on thesame route again, then the routing probability can be shifted again,repeating this process until the congestion has stabilized.

FIG. 12 illustrates example operations 1200 for returning a latencyprobe packet. A receive operation 1202 receives a latency probe packeton a first leg of a round trip. The latency probe packet is associatedwith a specific flow and was transmitted from a source switch to adestination switch with a direction value set to indicate the first legof the round trip. A queuing operation 1204 inserts a latency probepacket into a transmit queue associated with the destination node of theflow. A decision operation 1206 monitors the transmit queue to determinewhen the latency probe packet reaches the head of the transmit queue.

When the latency probe packet reaches the end of the transmit queue, adequeuing operation 1208 removes the latency probe packet from thetransmit queue and modifies it to travel on its return leg of the roundtrip back to the source switch. For example, the source identifier anddestination identifier are swapped in the latency probe packet and thedirection value is set to identify the return leg of the round trip. Atransmission operation 1210 transmits the latency probe packet to thesource switch on the return leg of its round trip.

FIG. 13 illustrates an example switch architecture 1100 configured toimplement dynamic latency-based rerouting. In the illustratedarchitecture, the switch represents a Fibre Channel switch, but itshould be understood that other types of switches, including Ethernetswitches, may be employed. Port group circuitry 1302 includes the FibreChannel ports and Serializers/Deserializers (SERDES) for the networkinterface. Data packets are received and transmitted through the portgroup circuitry 1302 during operation. Encryption/compression circuitry1304 contains logic to carry out encryption/compression ordecompression/decryption operations on received and transmitted packets.The encryption/compression circuitry 1304 is connected to 6 internalports and can support up to a maximum of 65 Gbps bandwidth forcompression/decompression and 32 Gbps bandwidth forencryptions/decryption, although other configurations may support largerbandwidths for both. Some implementations may omit theencryption/compression 1304. A loopback interface 1306 is used tosupport Switched Port Analyzer (SPAN) functionality by looping outgoingpackets back to packet buffer memory.

Packet data storage 1308 includes receive (RX) FIFOs 1310 and transmit(TX) FIFOs 1312 constituting assorted receive and transmit queues. Thepacket data storage 1308 also includes control circuitry (not shown) andcentralized packet buffer memory 1314, which includes two separatephysical memory interfaces: one to hold the packet header (i.e., headermemory 1316) and the other to hold the payload (i.e., payload memory1318). A system interface 1320 provides a processor within the switchwith a programming and internal communications interface. The systeminterface 1320 includes without limitation a PCI Express Core, a DMAengine to deliver packets, a packet generator to supportmulticast/hello/network latency features, a DMA engine to uploadstatistics to the processor, and top-level register interface block.

A control subsystem 1322 includes without limitation a header processingunit 1324 that contains switch control path functional blocks. Allarriving packet descriptors are sequenced and passed through a pipelineof the header processor unit 1324 and filtering blocks until they reachtheir destination transmit queue. The header processor unit 1324 carriesout L2 Switching, Fibre Channel Routing, LUN Zoning, LUN redirection,Link table Statistics, VSAN routing, Hard Zoning, SPAN support, andEncryption/Decryption.

The control subsystem 1322 is also illustrated as including latencymanagement logic 1326, rerouting logic 1328, and a latency map 1330(e.g., a memory-resident data table). In one implementation, the latencymanagement logic 1326 constructs, deploys, and receives the latencyprobe packets via the available routes. The latency management logic1326 also manages the latency map 1330, including one or more of thefollowing: recording the transmission time stamps, computing TEff formultiple routes, detecting latency conditions, identifying the lowerlatency routes relative to a congested or higher latency route, etc.When a better route is identified (e.g., in response to a latencycondition), the routing logic 1328 adjusts the routing of one or moreflows. For example, the probability of routing flows to the lowerlatency route can be increased to create a dynamic shift of flow trafficto the lower latency route. Furthermore, the rerouting logic 1328 canalso decide to hold flow traffic through a higher latency route for awaiting period and thereafter shift that flow traffic to an alternativelower latency route.

A network switch may also include one or more processor-readable storagemedia encoding computer-executable instructions for executing one ormore processes of dynamic latency-based rerouting on the network switch.It should also be understood that various types of switches (e.g., FibreChannel switches, Ethernet switches, etc.) may employ a differentarchitecture that that explicitly describe in the exemplaryimplementations disclosed herein.

The embodiments of the invention described herein are implemented aslogical steps in one or more computer systems. The logical operations ofthe present invention are implemented (1) as a sequence ofprocessor-implemented steps executing in one or more computer systemsand (2) as interconnected machine or circuit modules within one or morecomputer systems. The implementation is a matter of choice, dependent onthe performance requirements of the computer system implementing theinvention. Accordingly, the logical operations making up the embodimentsof the invention described herein are referred to variously asoperations, steps, objects, or modules. Furthermore, it should beunderstood that logical operations may be performed in any order, unlessexplicitly claimed otherwise or a specific order is inherentlynecessitated by the claim language.

The above specification, examples, and data provide a completedescription of the structure and use of exemplary embodiments of theinvention. Since many embodiments of the invention can be made withoutdeparting from the spirit and scope of the invention, the inventionresides in the claims hereinafter appended. Furthermore, structuralfeatures of the different embodiments may be combined in yet anotherembodiment without departing from the recited claims.

1. A network source switch comprising: latency management logicconfigured to identify a lower latency route from the network sourceswitch responsive to detection of a latency condition on a higherlatency route from the network source switch; and rerouting logicconfigured to adjust routing of one or more flows through the networksource switch, the adjusted routing lowering the latency of the higherlatency route.
 2. The network source switch of claim 1 furthercomprising: a latency map configured to record one or more effectivelatency time measures associated with routes available from the networksource switch.
 3. The network source switch of claim 2 wherein the oneor more effective latency time measures are computed using a weightedrunning average of latencies detected over time on each route.
 4. Thenetwork source switch of claim 1 wherein the latency management logic isfurther configured to measure one or more latencies associated withroutes available from the network source switch.
 5. The network sourceswitch of claim 4 wherein the latency management logic is furtherconfigured to record in a latency map one or more effective latency timemeasures associated with latencies measured for the route.
 6. Thenetwork source switch of claim 1 wherein the rerouting logic is furtherconfigured to adjust routing of flows through the network source switchby increasing a probability that a flow is routed via the identifiedlower latency route.
 7. The network source switch of claim 1 wherein thererouting logic is further configured to adjust routing of flows throughthe network source switch by decreasing a probability that a flow isrouted via the higher latency route.
 8. The network source switch ofclaim 1 wherein the latency management logic is configured to deploylatency probe packets via routes available from the network sourceswitch.
 9. The network source switch of claim 8 wherein the latencymanagement logic is configured to receive the latency probe packets asthey are returned to the network source switch by a destination switchof a route and to compute an effective latency time measure of the routebased on a round trip times of the latency probe packets.
 10. Thenetwork source switch of claim 8 wherein the latency management logic isconfigured to receive the latency probe packets as they are returned tothe network source switch by a destination switch of a route, whereinthe latency probe packets have reached the head of a transmit queue ofthe destination switch before being returned to the network sourceswitch.
 11. The network source switch of claim 1 wherein the latencymanagement logic is configured to deploy and receive latency probepackets over time to update an effective latency time measure of theroute in a latency map.
 12. The network source switch of claim 1 whereinthe rerouting logic is further configured to adjust routing of a flowfrom the higher latency route to the lower latency route.
 13. A methodcomprising: identifying a lower latency route from a network sourceswitch responsive to detection of a latency condition on a higherlatency route from the network source switch; and adjusting routing ofone or more flows through the network source switch, the adjustedrouting lowering the latency of the higher latency route.
 14. The methodof claim 13 further comprising: recording in a latency map one or moreeffective latency time measures associated with routes available fromthe network source switch.
 15. The method of claim 14 wherein the one ormore effective latency time measures are computed using a weightedrunning average of latencies detected over time on each route.
 16. Themethod of claim 13 wherein the latency management logic is furtherconfigured to measure one or more latencies associated with routesavailable from the network source switch.
 17. The method of claim 16further comprising: recording in a latency map one or more effectivelatency time measures associated with latencies measured for the route.18. The method of claim 13 wherein the adjusting operation comprises:adjusting routing of flows through the network source switch byincreasing a probability that a flow is routed via the identified lowerlatency route.
 19. The method of claim 13 wherein the adjustingoperation comprises: adjusting routing of flows through the networksource switch by decreasing a probability that a flow is routed via thehigher latency route.
 20. The method of claim 13 further comprising:deploying latency probe packets via routes available from the networksource switch.
 21. The method of claim 20 further comprising: receivingthe latency probe packets as they are returned to the network sourceswitch by a destination switch of a route and to compute an effectivelatency time measure of the route based on a round trip times of thelatency probe packets.
 22. The method of claim 20 wherein the receivingoperation comprises: receive the latency probe packets as they arereturned to the network source switch by a destination switch of aroute, wherein the latency probe packets have reached the head of atransmit queue of the destination switch before being returned to thenetwork source switch.
 23. The method of claim 13 further comprising:deploying and receiving latency probe packets over time; and computingan effective latency time measure of the route based on round trip timesof the latency probe packets to update the effective latency timemeasure of the route recorded in a latency map.
 24. The method of claim13 wherein the adjusting operation comprising: adjusting routing of aflow from the higher latency route to the lower latency route.
 25. Oneor more processor-readable storage media encoding processor-executableinstructions for executing on a network source switch a processcomprising: identifying a lower latency route from the network sourceswitch responsive to detection of a latency condition on a higherlatency route from the source switch; and adjusting routing of flowsthrough the network source switch, the adjusted routing lowering thelatency of the higher latency route.